fix: remove the v4-migration legacy key from local storage#8353
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughAppProvider's initial mount effect now removes the ChangesLegacy Storage Cleanup
Estimated code review effort: 1 (Trivial) | ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Co-authored-by: Prateek Sunal <41370460+prateekmedia@users.noreply.github.com>
c7e33d6 to
6516961
Compare
Description
Jira
v4-migration local storage key was introduced as a temporary migration notice for v3.5.x builds, warning them about affected APIs in their scripts.
In v4 that key becomes redundant, so this PR removes it.
Summary by CodeRabbit